Configuring the Nodinite Windows Server Monitoring Agent

Info

This guide provides instructions for configuring the Monitoring of Windows Servers using the Nodinite Windows Server Monitoring Agent.

Note

The Monitoring and the remote configuration is available if you first install and create the initial Monitoring Agent Configuration for the Windows Server Monitoring Agent. First-time users start here.

The Nodinite Windows Server Monitoring Agent account must be a local administrator on the target server to monitor; Make sure to review the Prerequisites.

The agent performs Monitoring according to the user-defined configuration per Group.

Remote Configuration

As a Nodinite Administrator, click the 'Configuration' button to open a modal to configure the agent:

Click the 'Configuration' button to open a dialog for configuring the agent.

Many specific configurations can also be made directly on the Resource using the Action button if the Monitor View uses Remote Actions feature enabled.

You must be a Nodinite Administrator to Manage the collection of Windows Servers.

Add Group

The Windows Server Groups tab holds an array with zero or more Group configurations.

Here's an example of the Windows Server Groups tab.

• Press the Add button to add one (or more) Group(s):
  
  Here's an example of a Group configuration; it is one Accordion per configuration.

  Repeat this step for each unique Group of Windows Servers to monitor with Nodinite.

To manage the configuration; Click the caret down icon to expand the Group accordion. There are a number of features with Monitoring thresholds and settings within the Tabs:

Tabs

• General tab
• Servers
• Certificate tab
• CPU tab
• Disk tab
• Event Log tab
• IIS Tab
• Memory tab
• Network Tab
• Ping tab
• PowerShell tab
• Scheduled Tasks tab
• Windows Services tab

General Tab

Click the General tab to manage essential information about the Group with Windows Servers to include in the Monitoring.

Here's an example of the 'General' tab.

• Enabled - When checked, enable the Monitoring of Windows Servers in this Group.
  
  Here's an example of an Enabled Group configuration.

  Here's an example of a Disabled Group configuration.

• Name - The name of this Group configuration.

• Description - Specify a user-friendly short description of this Group configuration.

Servers Tab

You can include zero or more Windows Servers in the Group. A Windows Server can only exist in one group. Duplicates are not allowed.
Click on the Add button to add a new Windows Server to include in the Monitoring.

• Enabled - When checked, enable the Monitoring of this Windows Server.
  
  Here's an example of an Enabled Windows Server configuration.

  Here's an example of a Disabled Windows Server configuration.

• Display Name - The display name to use for this Resource.

  Resources group per entry using the Application naming concept.
  
  Here's an example of the Application filter using the Display Name.
  ![!NOTE] Changing the name may require reconfiguration of affected Monitor Views.

• Description - Specify a user-friendly short description of this Group configuration.

• Host-name or IP address - The host-name or IP address of the Windows Server to include in the Monitoring.

Settings tab

From within the Settings tab, you provide some details that determine the operation behaviour of the Windows Server Monitoring Agent.

• Environment
• Debug
• Culture Information

Here's an example of the Settings tab.

Environment

Part of the common features shared with all Monitoring Agents, there is an option to set the name of the target Environment, for example, TEST, QA, PROD.

Debug

Part of the common features shared with all Monitoring Agents, there is an option to set the Debug flag for additional file logging that can be enabled/disabled as needed. Default is unchecked.

Culture Information

The Culture Information setting determines how time-based data from this agent is presented in the Web Client/Web API.

Save

You must click 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.

Here's an example of the Save options.

Note

The delay in presenting the new evaluated state depends on the synchronization interval set for the Monitoring agent. Click the Sync Now button to force an immediate synchronization.

Save and close, save, and close the dialogue.
Cancel, closes the dialogue without saving any changes.

---

Add Windows Server Monitoring Agent Configuration

After the successful installation of the Windows Server Monitoring Agent you must provide Nodinite with connection details, so the Monitoring Service knows there's a new guy in town.

No Monitoring or other configuration of the Windows Server Monitoring Agent can be performed before the steps outlined below has been executed.

Configuration Steps

1. Add and configure a new Monitoring Agent Configuration

   Connection information is available in the README.txt file in the installation folder

2. Use the Remote Configuration feature to configure the agent. Detailed at the beginning of this user guide.

3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Windows Server Monitoring Agent according to business needs.

   Add or manage Monitor View

4. Fine-tune specific settings directly on Resources using Remote Actions.

---

Next Step

Add or manage a Monitoring Agent Configuration
Add or manage Monitor View
Update

Related

Install Windows Server Monitoring Agent
Monitoring Agents
Applications